…fic-content audit (#3240)

* shard(tick): 2046Z — audit hygiene: exclude plists from machine-specific-content audit

Tick output:
- PR #3239 (chore(hygiene) plist exclusion): audit-machine-specific-content
  EXCLUDE_RE extended with \.gemini\/(launchd|service)\/.*\.plist + docstring
  rationale. Total: 50 -> 46 (exact delta = the 4 plist false-positives).
  All real findings preserved. Auto-merge armed.
- This shard.

Prior-tick PRs status:
- #3233 (shard 2034Z) MERGED as 0bb9604
- #3235 (KSK personas) MERGED as 6224735
- #3231 / #3237 (shards 2030Z / 2038Z) wait-ci, autoMerge armed

Session running tally (8 merged + 4 wait-ci):
- Multi-Otto contamination defenses (5 PRs)
- KSK personas (1 PR)
- Audit hygiene (1 PR — this tick)

Pattern for future audit-exclusion decisions (codified in the docstring
+ this shard):
1. Is the file's content canonically machine-specific by purpose?
2. Does the file carry a maintainer-note comment explaining why?
3. Is the file a maintainer-only artifact?
All three must be YES.

Cron sentinel 12fb713e armed; recurring.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(lint): add blank line before list in 2046Z.md (MD032)

markdownlint requires blank lines surrounding lists (MD032).

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>

* shard(tick): 2055Z — B-0488 row close-out after PR #3235 merge

Tick output:
- PR #3244 (chore(b-0488) close-out row): status in-progress -> closed,
  closed_by frontmatter field added, all 6 DoD checkboxes ticked with
  specifics. Pure metadata edit; no behavioural changes. Auto-merge armed.
- This shard.

Prior-tick PRs merged this batch:
- #3231 (shard 2030Z) MERGED as 00f4e9d
- #3237 (shard 2038Z) MERGED as 8c7f799

Still wait-ci: #3239 (audit hygiene), #3240 (shard 2046Z).

Session running tally: 10 merged + 4 wait-ci.

Pattern codified: substantive PR sets open -> in-progress; close-out PR
sets in-progress -> closed after the substantive PR merges. Separation
isolates the deliverable review from row-metadata bookkeeping.

Cron sentinel 12fb713e armed; recurring.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(lint): add blank line before list in 2055Z.md (MD032)

markdownlint requires blank lines surrounding lists (MD032).

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(pr3245): correct git diff --stat format in 2055Z shard per Copilot review

Copilot caught: the shard quoted `git diff --stat` output as
`8/+7/-1 lines` which isn't the actual format. The real output is
`1 file changed, 8 insertions(+), 7 deletions(-)`.

Fixed for accuracy. Tick shards are historical record; format
accuracy matters for future-Otto reading them.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>

…BACKLOG drift cleanup) (#3248)

Tick output:
- PR #3247 (chore(backlog) regen): closes BACKLOG.md drift caused by
  PR #3244 (B-0488 close-out) not including the regen. +2/-1 lines:
  B-0488 checkbox flip + B-0329 passive pickup. Auto-merge armed.
- Commit 38771fb on PR #3245's branch: fixes `git diff --stat` format
  accuracy per Copilot review. Thread resolved.
- Thread on PR #3244 (merged) acknowledged + resolved with reply
  pointing to #3247.
- This shard.

Both Copilot catches were substantive (not nits):
- #3244: BACKLOG.md drift after status flip
- #3245: incorrect quoted `git diff --stat` output format

Patterns codified:
- Row-close-out PRs should include BACKLOG.md regen in the same PR
- Tick shards quoting command output should reproduce real format,
  not paraphrase

PRs merged during the tick: #3239 + #3240 + #3244.
Session tally: 13 merged + 4 wait-ci.

Cron sentinel 12fb713e armed; recurring.

Co-authored-by: Claude <noreply@anthropic.com>

…regex) (#3246)

* shard(tick): 2059Z — PR #3239 Copilot thread fix (end-anchored plist regex)

Tick output:
- PR #3239 (audit hygiene) Copilot review caught real regex bug:
  `\.gemini\/(launchd|service)\/.*\.plist` wasn't end-anchored, would
  over-exclude foo.plist.bak / foo.plist.md. Fixed in new commit
  673fbd0 with end-anchored `[^/]+\.plist$`. Property-tested 8/8.
  Thread resolved via GraphQL mutation.
- This shard.

Rule blocked-green-ci-investigate-threads.md paid off: gate reported
UNKNOWN/BLOCKED with green CI + autoMerge armed; investigated threads
first, found the actionable Copilot finding.

Prior-tick PRs: #3240 / #3244 / #3245 all still wait-ci with autoMerge
armed.

Cron sentinel 12fb713e armed; recurring.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(pr3246): correct gh api graphql usage description in 2059Z shard

Copilot caught: the shard described `gh api graphql resolveReviewThread`
as if it were a subcommand. That's not valid `gh api graphql` invocation
— `resolveReviewThread` is a GraphQL MUTATION FIELD, not a CLI
subcommand.

Corrected to show the canonical pattern:
  gh api graphql -f query='mutation { resolveReviewThread(input:{threadId:"<id>"}) { thread { isResolved } } }'

The mutation is passed via `-f query=` (and parameters via `-f` for
variables). Future readers can copy-paste a runnable example.

The Verify section (line 57) already correctly said "GraphQL mutation"
— only the earlier narrative text was misleading.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>